Repository navigation
Build a responsive 3D assembly for the homepage hero - #455
Merged
Merged
Conversation
This was referenced Nov 12, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Advances #7 and follows #453.
The previous scene moved between absolute positioning and grid placement, and the hero height dropped 350px between 660px and 661px. At 768px, the Paperwork and Launch Kit previews were cropped by the edge of the viewport.
One responsive grid now owns the layout and reserves space for an exploded assembly built with the approved mark and actual product imagery. A short assembly motion and route pulse run once. Fine-pointer hover tilts the art inside its frame. Reduced motion shows the complete resting state.
Local Chromium covered the geometry across 12 widths between 320px and 1728px, both themes, pointer tilt and reset, reduced motion, keyboard navigation to Get Ready, and the static no-JavaScript path. Reviewed the actual desktop and phone rendering. Production evidence goes in #11.